Fix migration mojibake and broken links; report remaining link issues#19
Merged
Merged
Conversation
Repair double-encoded UTF-8 artifacts introduced during the WordPress migration. Non-breaking spaces and Latin-1 symbols were double-encoded, producing a stray "Â" before each character (byte sequence C3 82 C2 xx) that rendered as visible garbage across ~400 pages. Reverse the encoding by dropping the spurious C3 82 prefix, restoring nbsp, ®, ·, «, ½, and µ. Also remove 7 isolated leftover "Â" artifacts in podcast show notes. Fix a malformed nested Markdown link on the 2023-11-06 podcast episode (akasearch.net) that rendered with URL-encoded brackets. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QWdScrWP32GB7vZBjx87Jd
✅ Deploy Preview for powershellorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
These are local build tooling artifacts from installing hugo-extended via npm to render and audit the site; they should not be tracked. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QWdScrWP32GB7vZBjx87Jd
This was referenced Jun 20, 2026
therealgill
approved these changes
Jun 20, 2026
therealgill
left a comment
therealgill
left a comment
There was a problem hiding this comment.
Spot checked, Appears to be fine
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link & rendering review of PowerShell.org
I built the site locally with Hugo (v0.155.3 extended) and audited the full rendered output (4,377 HTML pages, ~7,450 distinct external URLs) plus the Markdown source for broken links and misrendered content. This PR fixes the two clear, mechanical issues and reports the rest below for a maintainer decision (the right fix is ambiguous).
✅ Fixed in this PR
1. Double-encoded UTF-8 "mojibake" across ~400 pages
During the WordPress → Hugo migration, non-breaking spaces and Latin-1 symbols were double-encoded, leaving a stray
Âbefore each character (byte patternC3 82 C2 xx). This rendered as visible garbage on the live site, e.g.:Azure runs Linux _just fine. _Huzzah!PowerShell and PowerGUI®The fix reverses the encoding by dropping the spurious
C3 82prefix, restoring the intendednbsp,®,·,«,½, andµ. 7,939 sequences across 404 files, plus 7 isolated leftoverÂartifacts in podcast show notes. After the fix, zeroÂartifacts remain in the rendered HTML.2. Malformed nested Markdown link (
content/podcast/2023-11-06-...merrill-fernandos-toolbox...)[akasearch.net]([http://akasearch.net](http://akasearch.net))rendered with URL-encoded brackets. Corrected to a single clean link.📋 Reported — needs a maintainer decision (not changed here)
3. Broken internal links to old WordPress sections that no longer exist
Reference-style links in ~10 historical articles point to paths that 404 on the new site. Targets are ambiguous (some content is simply gone), so I left them untouched:
/discuss/https://forums.powershell.org?2013-02-11-winter-scripting-camp-the-post-mortem.md/newsletter/2013-04-05-coming-tips-for-the-scripting-games.md/games/2013-04-06-2013-scripting-games-mighty-panel-of-celebrity-judges.md/people/,/members/authors/?2013-04-15-changes-coming-to-powershell-org.md,2018-10-24-powershell-org-site-status-update.md/ebooks/,/videos/2016-06-24-heres-what-youve-missed...md/wp/newsletter2013-07-23-techsessions-free-powershell-webinars.mdNote: some of these reference definitions also have mismatched link titles (e.g.
[1]: /newsletter/ "PowerShell Script that Relaunches as Admin"), suggesting the migration tool collapsed several distinct URLs onto one wrong target.4. Broken relative links in
content/articles/2019-06-14-universal-dashboard-templates-...md:[…](the-why)and[…](the-how)resolve to nonexistent pages — they were likely in-page anchors in the original.5. Scheme-less / malformed links rendered as relative:
twitter.com/jeffhicks(nohttps://) in2013-04-22-meet-the-scripting-games-judges-jeffery-hicks.mdand2013-02-16-phillyposh-...md.6. Two pages drop content as "raw HTML omitted" (Hugo
markup.goldmark.renderer.unsafe: false):content/podcast/2013-08-14-episode-238-...scriptcs.md— the IRC chat log uses<nickname>angle brackets, so those lines are stripped from the page.content/articles/2011-05-18-configuring-rbac-for-mobileshell-...md— an embedded<?xml?>block and HTML comments are dropped.Recommended fix: escape the angle brackets (or wrap the IRC log in a fenced code block) rather than enabling
unsafeglobally.Verification
hugo --gc --minifybuilds cleanly (only the two pre-existing "raw HTML omitted" warnings remain, item 6 above).🤖 Generated with Claude Code
Generated by Claude Code